Repository navigation
fix(usage): repair zero-reported input_tokens on non-trivial requests (#10705) - #10757
Merged
Merged
Conversation
muhamadgalihsaputra
pushed a commit
to niyatna/NiyatnaRoute
that referenced
this pull request
Sep 27, 2026
…cheaper-inference#10705) (cheaper-inference#10757) Co-authored-by: Markus Hartung <mail@hartmark.se>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #10705
Root cause:
sanitizeProviderUsageForRequest()inopen-sse/utils/usageTracking.tsshort-circuited on ANYreportedInput <= 0, treating a provider-reportedinput_tokens: 0as automatically acceptable and skipping the local-estimate fallback — even for a real, non-trivial request body. A third-party Claude-compatible relay under-reporting to exactly 0 was passed straight through into stats/logging.Fix: only treat
reportedInput === 0as plausible when the request body itself is trivial (no serialized body, or 0 bytes); otherwise repair with the existing local tokenizer estimate, same as the over-report path.Regression test: tests/unit/usage-tracking-zero-input-tokens-10705.test.ts. Verified no regression against the existing over-report guard (tests/unit/stream-impossible-input-usage.test.ts, 8331-usage-buffer-inflation.test.ts, usage-token-buffer.test.ts — 49 tests, all green).